Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventProcessor.ps #2

Merged
merged 4 commits into from
Feb 6, 2022
Merged

EventProcessor.ps #2

merged 4 commits into from
Feb 6, 2022

Conversation

github-learning-lab[bot]
Copy link

Step 3: Add headers

As you saw on your website, your portfolio doesn't have much content yet. We'll learn how to edit the file in this pull request to incorporate some Markdown headers.

You can see an example of a header at the top of this page! Just like in HTML, a header is a larger bit of text at the beginning of a section. There are six sizes.

Example

# This is an <h1> header, which is the largest
## This is an <h2> header
###### This is an <h6> header, which is the smallest

How it looks

This is an <h1> header, which is the largest

This is an <h2> header

This is an <h6> header, which is the smallest

In issues, pull requests, and comments, you can use the text formatting toolbar.

The toolbar isn't available everywhere. When you edit a file, you must type the # symbols manually.

⌨️ Activity: Edit your file with headers

  1. In this pull request, click the Files changed tab.
  2. To edit the file titled _includes/01-name.md, click the small pencil ✏️ or select "Edit file" from the three dotted ... menu in the upper right corner of the file view.
  3. On the Edit file tab, add a #, followed by a space, before the content to make it an H1 Header. You can add more headers, using one to six # characters followed by a space.
  4. Above your new content, click Preview changes.
  5. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.
  6. Click Commit changes.

Watch below for my response.

@github-learning-lab
Copy link
Author

Step 4: Merge your headers

I see you've added at least one header, @chrisspradling1980. You can continue working if you'd like, otherwise let's merge 📖 this pull request and move on with the course.

⌨️ Activity: Merge the Pull Request

  1. Click Merge pull request below.

Watch below for my response!

@chrisspradling1980
Copy link
Owner

Changed my name, created the header content and merged the pull request.

@chrisspradling1980 chrisspradling1980 merged commit 0a59a3b into main Feb 6, 2022
@github-learning-lab
Copy link
Author

Nice headers, @chrisspradling1980! You can see your work here: https://chrisspradling1980.github.io/markdown-portfolio/

⌨️ Activity: Delete your branch

  1. Delete your branch 📖 in this pull request.

Go to the next pull request now!

@chrisspradling1980 chrisspradling1980 changed the title Give your portfolio a header EventProcessor.ps1 Feb 17, 2022
@chrisspradling1980 chrisspradling1980 changed the title Give your portfolio a header EventProcessor.ps1 Feb 17, 2022
@chrisspradling1980 chrisspradling1980 changed the title Give your portfolio a header EventProcessor.ps1 Feb 17, 2022
@chrisspradling1980 chrisspradling1980 changed the title EventProcessor.ps1 EventProcessor.ps Feb 17, 2022
@chrisspradling1980 chrisspradling1980 linked an issue Mar 15, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

My picture for this tutorial
2 participants